APAR= II09523  
CLIENT ACCESS FOR WINDOWS 95 SERVICE PACK INFORMATION

ERROR DESCRIPTION:

** Last updated 7/15/97 **

CLIENT ACCESS FOR WINDOWS 95 PTF INFORMATION
____________________________________________

You will notice a change in how fixes are built and distributed
in the IBM Windows 95 client.  In the past each PTF would
contain a near one to one ratio of APAR to PTF. With this client
you may occasionally hear a PTF referred to as a 'Service Pack'
or 'Service Pack PTF.'  This single PTF will contain fixes and
enhancements for multiple APARs. Each PTF (Service Pack) is
cumulative and contains all fixes that are available when
the PTF is built.  Therefore, each PTF will supersede all
previous PTFs.  How PTFs can be ordered and applied has also
changed.  It is now possible to obtain a PTF file from an IBM
FTP site (ftp.software.ibm.com) or link to the FTP site from the
Client Access Technical Support page on the web:

     http://as400service.rochester.ibm.com/webhome.nsf/cahome

PRE-REQUISITE PTF - One of the following operating system PTFs
must be applied (APAR SA53988).  The PTF will allow the
application and removal of PTFs for the Windows 95 client
(5763XD1).  See informational APARs II09920 (V3R1M0), II09921
(V3R1M1), or II10303 (V3R1M2) for additional recommended PTFs.

    V3R1M0 systems: SF31393
    V3R2M0 systems: SF31498
    V3R6M0 systems: SF31544

*** Please Note ***
 If your AS400 system is running V3R1 or V3R6 you must use
 DSPSFWRSC to verify that 5763XD1 is installed.


CLIENT ACCESS FOR WINDOWS 95 PTFs (Service Packs) for V3R1M0:
_____________________________________________________________

      PTF #              Available   Installed file dates
      -----              ---------   --------------------

      Base code           06/21/96        05/09/96
      SF31778             06/21/96        06/21/96
      SF33616             08/19/96        08/04/96
      SF35514             10/17/96        08/06/96
      SF36095             11/07/96        08/07/96
      SF36717             01/21/97        08/08/96
      SF38346             02/25/97        08/09/96
      SF39053 (twinax)    03/07/97        08/10/96
      SF39582             03/28/97        08/11/96
      SF40785             05/30/97        08/12/97

  No more service packs are planned for Mod 0.
  Please note that this may change based on the
  criticality of fixes that may be required.

NOTE: SF39053 contains the twinax support as well as the fixes
  contained in SF38346.

CLIENT ACCESS FOR WINDOWS 95 PTFs (Service Packs) for V3R1M1:
____________________________________________________________

      PTF #              Available   Installed file dates
      -----              ---------   --------------------

      Base code           11/08/96        11/08/96
      SF35403             10/11/96        12/03/96
      SF35935             10/17/96        12/04/96
      SF36096             11/13/96        12/05/96
      SF36801             01/21/97        12/06/96
      SF38281             02/25/97        12/07/96
      SF39059 (twinax)    03/07/97        12/08/96
      SF39584             03/31/97        12/09/96
      SF40081 (defective) 05/04/97        12/10/96
      SF41118             06/16/97        12/11/96
      SF41491             07/07/97        12/12/96

  Target availability date for next service pack is 08/30/97.
  Please note that this date may change based on the
  criticality of fixes going into the service pack.

 NOTE: SF39059 contains the twinax support as well as the fixes
   contained in SF38281.

CLIENT ACCESS FOR WINDOWS 95/NT PTFs (Service Packs) for V3R1M2:
_______________________________________________________________

      PTF #              Available   Installed file dates
      -----              ---------   --------------------

      Base code           02/28/97        01/12/97
      SF37523             02/12/97        02/01/97
      SF39220             03/14/97        02/02/97
      SF39669 (defective) 05/04/97        02/03/97
      SF40828             06/16/97        02/04/97

  Target availability date for next service pack is 08/08/97.
  Please note that this date may change based on the
  criticality of fixes going into the service pack.


HOW TO ORDER A SERVICE PACK PTF:
________________________________

    1.  Order through ECS with the SNDPTFORD command.  The PTF
        order will take a long time to order this way especially
        if the pre-req/co-req PTFs do not already exist on your
        system.  Consider selecting *ANY for the delivery
        method (DELIVERY) parameter so that the PTF(s) are
        delivered by mail.

    2.  An auto-extracting zip file of the PTF can be down-
        loaded from an FTP site, ftp.software.ibm.com.
        The directory structure is:

'/as400/products/clientaccess/win32/v3r1mx/servicepack/sfxxxxx'
                    x = modification level

   3.  The same auto-extracting service pack PTF file
       can be obtained from the Client Access Home page
       on the web.  The URL is
   http://as400service.rochester.ibm.com/webhome.nsf/cahome/
       Select the option to access the FTP site.

HOW TO APPLY A SERVICE PACK PTF:
________________________________

    1.  If the PTF is ordered through ECS, then use the normal
        PTF install method (LODPTF, APYPTF, etc.).  The next
        time the Client Access 'Check Version' program runs
        from the PC, you will be prompted to replace the old
        programs with the new ones.

        The service pack READMESP.TXT file contains details on
        how to install the service pack to your PC in various
        environments.  After installing the Service Pack PTF on
        your AS/400 you can view the READMESP.TXT file on the PC
        by mapping a network drive to QCA400 on the AS/400 and
        then looking at the file:

           QCA400WIN32SERVICECDROMREADMESP.TXT (V3R1M0 and
                                                    V3R1M1)

           or

           QCA400WIN32SERVICEIMAGEREADMESP.TXT (V3R1M2)

        where the "" in the directory structure should really
        be changed to backslashes.

       If 'Check Version' does not run automatically from a
       workstation, the 'Check Service Pack Level' program can
       be started manually from the Client Access Accessories
       folder.

   2.  If the PTF files are obtained through the FTP site,
       then the files can be installed directly on the PC.
       Create a directory on the workstation or a server
       and run the SETUP program on the target workstation.
       If the Service Pack has been extracted on to a diskette,
       then the SETUP program can be executed from the A:
       drive, also.


       * * * IMPORTANT * * *
       Read Informational APAR II09220.  That APAR will contain
       important product information and refer to other
       informational APARS containing lists of co-req PTFs for
       the OS/400 operating system.  The easiest way to ensure
       that the necessary co-reqs are ordered and applied is to
       order and apply using the ECS method above.

HOW TO REMOVE A SERVICE PACK PTF:
_________________________________

For the V3R1M0 client with any Service Pack PTF installed and
for the V3R1M1 client with Service Pack PTF SF35935 or prior
installed, there is not a way to remove a Service Pack PTF from
a PC.  Client Access must be removed from the PC through the
Windows 95 Install Shield and then reinstalled without the
Service Pack PTF.  To do this, click on the 'Add/Remove
Programs' icon located in the Windows 95 Control Panel.  Select
'IBM AS/400 Client Access for Windows 95' and click on the
'Add/Remove' button and follow the instructions on the screen.
Client Access can then be reinstalled.

For the V3R1M1 client with Service Pack PTF SF36096 or later
installed, to remove the service pack from your PC, click the
Windows 95 Start button, click on Settings, and then click on
click on the 'Add/Remove Programs' icon located in the Windows
95 Control Panel.  Select 'IBM Client Access for Windows 95
Service Pack SFxxxxx' and click on the 'Add/Remove' button and
follow the instructions on the screen.  Client Access should
then be at the previous Service Pack PTF level it was at before
installing the last Service Pack PTF.


